HBAnyware 3.2a14 Linux Installation Instructions

This installation kit contains the following components:

      HBAnyware version 3.2a14
      SSC version 3.2a14
      DFC Library version 2-15-1005
      Lputil version 2.0a14
      HBAAPI version 2.1.e

Dependencies:

HBAnyware requires that the lpfc driver module be installed.
The lpfc driver version 8.1.10.9 and all 8.1.10.x based driver releases are 
supported with this version of HBAnyware. 
This support includes the RHEL5 and SLES10-SP1 in-distro 8.1.10.3 lpfc driver.

HBAnyware requires a minimum screen resolution of 1024 x 768.


Installing HBAnyware:

 1. Copy the applications kit tar file to a directory on the install machine
 2. cd to the directory which you copied the tar file
 3. Untar the file: tar -xvf tarfilename 
 4. cd (change directory) to the "ElxLinuxApps.." directory created by step 3
 5. su to root
 6. If earlier HBAnyware version currently installed, type : ./uninstall
 7. Run the install script: ./install
 8. When prompted, answer the following question:

    Select desired mode of operation for HBAnyware

    1   Local Mode     : HBA's on this Platform can be managed by HBAnyware 
	clients on this platform only.
    2   Managed Mode   : HBA's on this Platform can be managed by local or 
	remote HBAnyware clients
    3   Remote Mode    : Same as '2' plus HBAnyware clients on this Platform 
	can manage local and remote clients.

	Enter the number '1' or '2' or '3'


 9. When prompted, answer the following question:
    
    Do you want to allow user to make subsequent management mode changes 
    using 'set_operating_mode' script
    Enter the letter 'Y' for yes or 'N' for no

10. Installation Complete: type /usr/sbin/hbanyware/hbanyware       
    to start GUI or type /usr/sbin/hbanyware/hbacmd list 
    to run script utility


Uninstalling HBAnyware

 1. Complete steps 1 through 5 from "Installing HBAnyware" above.
 2. Run the uninstall script: ./uninstall


Running the HBAnyware GUI

 1. su to root
 2. Run the script /usr/sbin/hbanyware/hbanyware 


HBAnyware Help:
To view the HBAnyware help pages or to access the Emulex Technical support 
pages you must have one of the following web browsers installed: mozilla, 
konqueror.


Helpful scripts

/usr/sbin/hbanyware/stop_hbanyware - This script will stop all HBAnyware
daemons and GUIs. Run this script before attempting to unload the lpfc driver.

/usr/sbin/hbanyware/start_elxhbamgr - This script will re-start the management
server daemon. Run this if you manually load the lpfc driver.

/usr/sbin/hbanyware/set_operating_mode - This script will re-issue the
HBAnywaremanagement mode configuration question described in installation 
step 8 above.

----------------------------------------------------------------------
Known Issues

1. Netlink (libnl) library package requirement
    1.1 Background
    1.2 Resolution
2. Virtual Connect backwards compatibility
    2.1 Background
    2.2 Resolution
3. Web Browsers and HBAnyware on-line help\
    3.1 Background
    3.2 Workaround
4. Kernel development environment requirement
    4.1 Background
    4.2 Resolution
5. libXp.so.6 dependency
    5.1 Background
    5.2 Resolution
6. libstdc++.so.5 dependency
    6.1 Background
    6.2 Resolution
7. PCI Loopback Test is not currently supported
    7.1 Symptoms
    7.2 Background
    7.3 Workaround
8. Incorrect reporting by lputil of HBA state in interactive mode
    8.1 Symptoms
    8.2 Background
9. Occasional batch download failures
    9.1 Symptoms
    9.2 Workaround 
10. Warning messages when no input is entered for mode of operation
    10.1 Symptoms
    10.2 Workaround

----------------------------------------------------------------------
1. Netlink (libnl) library package requirement

1.1 Background
    Certain libraries provided by this HBAnyware/applications kit have a 
    dependency on the distribution kernel's Netlink library (libnl). This 
    library package is installed by default when the RHEL5 or SLES10-SP1 
    distribution kernel is installed.

    On IA64 and AMD64/EM64T 64-bit architectures, the distribution by 
    default installs the native 64-bit libnl library package. To support 32-bit
    applications which depend on HBAnyware components (i.e. HBAAPI libraries), 
    the 32-bit libnl library package will need to be installed separately from 
    the distribution.

    On i386 and PPC architectures, the distribution installs by default the 
    32-bit libnl library package. On PPC architecture to support 64-bit 
    applications which depend on HBAnyware components (i.e. HBAAPI libraries), 
    the 64-bit libnl library package will need to be installed separately from 
    the distribution.

    Note that HBAnyware utilities (i.e. hbanyware, hbacmd) are not affected by
    this issue. The proper variant of HBAnyware utilities will be installed to 
    match the default installed libnl library package.

1.2 Resolution
    The installation process of this HBAnyware/applications kit will warn the 
    user when the 32- or 64-bit missing libnl library package could be needed.
    Users who wish to support applications that depend on the missing libnl 
    package will need to:

    i) Find and install the missing (32- or 64-bit) libnl library package from 
    the distribution media or distribution network. For SLES10-SP1 the YaST 
    management tool can be used for the installation.

    ii) Re-run the application kit's install script to install the related 
    HBAnyware components.


2. Virtual Connect backwards compatibility

2.1 Background
    Starting with HBAnyware version 3.2, Emulex provides support for LightPulse
    adapters that are reprogrammed with WWPNs outside the typical Emulex range,
    such as HP's upcoming Virtual Connect for Fibre Channel on the BladeSystem
    c-Class platform.  

2.2 Resolution
    In such environments, HBAnyware version 3.2 must be deployed across all 
    servers on the SAN, as well as any other management console used for 
    out-of-band management, so that all adapters appear in the discovery tree.


3. Web Browsers and HBAnyware on-line help

3.1 Background
   Some Web browsers attempt to continually reload the HBAnyware online help 
   rendering it unusable. 

3.2 Workaround
   In these cases, disable the Web browser's JavaScript capability. Please 
   refer to the Web browser's documentation for instructions.

4. Kernel development environment requirement

4.1 Background
   For RHEL4 and SLES9 installations only, this kit also includes the DFC
   helper module. Since this installation procedure builds the module for
   the currently running kernel, the kernel development environment must \
   be installed.
     
4.2 Resolution
   For systems running Red Hat Enterprise Linux (RHEL) 4, the appropriate 
   kernel-devel package is required; for example, a system with the 
   2.6.9-22.EL kernel would need the kernel-devel-2.6.9-22.EL package, 
   and a system with the 2.6.9-22.ELsmp kernel would need the 
   kernel-smp-devel-2.6.9-22.EL package.  For systems running SuSE Linux 
   Enterprise Server (SLES) 9, the appropriate kernel-source package is 
   required; for example, a system with the 2.6.5-7.139-bigsmp kernel 
   would need the kernel-source-2.6.5-7.139 package.

5. libXp.so.6 dependency

5.1 Background
   On RHEL5 installations on IA64 architectures, the HBAnyware GUI has a local 
   JRE/JVM that includes a dependency on the X-Windows libXp.so.6 shared object
   library. This file is part of the libXp-1.0.0-8.ia64.rpm on the RHEL5 OS 
   distribution. For SLES10, this file is part of the
   xorg-x11-devel-6.9.0-50.38.ia64.rpm package. 

5.2 Resolution
   In these cases, the HBAnyware start script will detect the absence of this 
   file and instruct the user accordingly. The appropriate RPM and any 
   dependencies must be loaded onto the host machine. For SLES10, this 
   libXp.so file is placed into the /usr/X11R6/lib directory. In this case,
   you should create a symbolic link for this file from this directory to 
   /usr/sbin/hbanyware/jre/lib


6. libstdc++.so.5 dependency

6.1 Background
   On RHEL5 installations on PPC64 architecture, the HBAnyware GUI has a local 
   JRE/JVM that includes a dependency on the libstdc++.so.5 shared object 
   library. This library might not be installed by default on your system.
 
   This dependency will  cause the following error when invoking the hbanyware 
   utility:
 
   # /usr/sbin/hbanyware/hbanyware
   Error loading: libstdc++.so.5: cannot open shared object file: No such file 
   or directory

6.2 Resolution
   In this case you should install the compat-libstdc++-33.ppc package from the
   RHEL5 distribution media or Red Hat Network 
   (compat-libstdc++-33-3.2.3-61.ppc.rpm). 


7. PCI Loopback Test is not currently supported

7.1 Symptoms
    An attempt to execute the PCI Loopback Test via the hbacmd utility is known
    to produce the following error: 

    # ./hbacmd loopback 10:00:00:00:c9:48:e9:9b 0 1 1 
    Running Loopback:  polling for results....
    Loopback - Result = General Error, time to execute = 1 ms.

7.2 Background
    The PCI Loopback Test is presently not supported due to a limitation in the
    underlying device driver management interface.

7.3 Workaround
    In order to verify the proper operation of the HBA a user could use the 
    Internal and/or External LoopBack Tests instead:

    # ./hbacmd loopback 10:00:00:00:c9:48:e9:9b 1 1 1
    or 
    # ./hbacmd loopback 10:00:00:00:c9:48:e9:9b 2 1 1


8. Incorrect reporting by lputil of HBA state in interactive mode

8.1 Symptoms
    Lputil will not correctly report the state of an HBA when run in 
    interactive mode. You might see state reported as "Other FFFC0000" as shown
    here:
      
        Host Adapter 0 (lpfc0) is an LP1050 (Other FFFC0000)
 
8.2 Background
    This is due to deprecated functionality in the underlying management 
    interface to the device driver. It does not cause functional failure.


9. Occasional batch download failures
 
9.1 Symptoms
    HBAnyware is currently experiencing intermittent problems with batch
    download operations in which three or more HBAs are specified as download 
    targets.  Downloads to one or more of the HBAs in your selected set of 
    download targets will occasionally fail for no apparent reason.
 
9.2 Workaround
    If you experience download failures during a batch download operation, 
    then you may retry downloads to the failed HBAs by performing the 
    following:
 
      - Click the 'Reset Display' button located to the right of the batch 
        download target list
      - Reselect all HBAs that failed the previous batch download operation
      - Deselect all HBAs that had completed successfully during the previous
        batch download operation
      - Click the 'Start Download' button to retry the failed downloads.


10. Warning messages when no input is entered for mode of operation

10.1 Symptoms
    During installation, if no mode of operation is entered when prompted, then
    after the Enter key is pressed the following warnings appear:

    ./set_operating_mode: line 49: [: -eq: unary operator expected
    ./set_operating_mode: line 76: [: -eq: unary operator expected
    ./set_operating_mode: line 102: [: -eq: unary operator expected

10.2 Workaround
     These messages do not affect the installation process and could be
     ignored.
     A correct mode of operation should then be entered to continure with the
     installation.

----------------------------------------------------------------------
                     
